Pornhub Ip Address
66.254.114.41 IP Address Details – IPinfo.io
IP address details
Waltham, Massachusetts, United States
Summary
Geolocation
Privacy
ASN
Company
Abuse
Hosted domains
Geolocation Data
City
Waltham
State
Massachusetts
Country
United States
Postal
02451
Local time
03:44 AM, Saturday, October 30, 2021
Timezone
America/New_York
Coordinates
42. 3986, -71. 2451
Geolocation API
IP geolocation lookup is the identification of an IP address’ geographic location in the real world.
Privacy Detection
Privacy Detection API
Detects various methods used to mask a user’s true IP address, including VPN detection, proxy detection, tor usage, or a connection via a hosting provider.
AS29789 – Reflected Networks, Inc.
ASN API
ASN details for every IP address and every ASN’s related domains, allocation date, registry name, total number of IP addresses, and assigned prefixes.
Reflected Networks, Inc.
Company API
Provides the company behind the IP address. This includes the company’s name, domain name, and what type of company it is: ISP, business, or hosting. ).
Abuse Details
US, MA, Waltham, 738 Main St PMB 140, 02451
+1-877-888-3800
Abuse Contact API
Our abuse contact API returns data containing information belonging to the abuse contact of every IP address on the Internet.
Hosted Domains API
Hosted domains API
Our Hosted Domains API, or Reverse IP API returns a full list of domains that are hosted on a single IP address.
What is my IP
Test our data accuracy by viewing insights from your IP address.
See your IP address
Map IPs
Paste up to 500, 000 IPs to see where they’re located on a map.
Try Map IPs
Summarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs
Pornhub.com Hosting Website Reviews – Myip.ms
Products
TOP World Hosting Companies (100, 000+)
World Hosting
USA
France
Gemany
United Kingdom
Russia
Other
Reports in Excel
Download IP WhoisDatabase in MySQL
TOP100 HostingCompanies
5, 500, 000 WorldWebsites Hosting Info
API Access to DB
Other Reports Excel »
Google bot visit time to your website
Free Button – Time ofLast Search BotsVisit to Your Website
Google Bot IP
Bing Bot IP Addresses
Yahoo Bot IP Addresses
Facebook Bot IP
Free GEO Information Box for Your Site
Add Free User IPInformation Boxon your site
on English
on Arabic
on French
on Russian
Other Languages
Latest Visitors Statistics Box
Cities SQL Database for Your Site
We provide Cities/States/Countries database in SQL / Mysql format for use on your website
All 252 World Countries
Nearly 2, 800 World States/Regions
More than 176, 000 of the Biggest World cities
Hosting Companies
TOP Best World Web Hosting Companies | Real-Time Statistics
World Hosting Companies DB (100, 000+ world hosting companies)
Report – Live Hosting Companies
Hosting Companies By Country
USA 7, 236, 914 sites
Germany 1, 854, 983 sites
Russia 593, 270 sites
Canada 561, 059 sites
Japan 381, 638 sites
Netherlands 364, 875 sites
France 333, 696 sites
United Kingdom 330, 598 sites
China 282, 708 sites
Turkey 207, 047 sites
Italy 177, 905 sites
Spain 167, 335 sites
Poland 160, 343 sites
Australia 157, 163 sites
Seychelles 139, 191 sites
Iran 138, 287 sites
South Korea 129, 285 sites
Czech Republic 113, 774 sites
India 106, 779 sites
Singapore 105, 898 sites
Ukraine 104, 264 sites
Vietnam 101, 907 sites
Virgin Islands, British 85, 547 sites
Hong Kong 81, 506 sites
Denmark 78, 905 sites
Switzerland 77, 713 sites
Brazil 75, 559 sites
South Africa 75, 151 sites
Cyprus 71, 271 sites
Sweden 59, 903 sites
Taiwan 48, 051 sites
Indonesia 47, 739 sites
Romania 46, 399 sites
Belgium 45, 849 sites
Hungary 42, 260 sites
Bulgaria 41, 875 sites
Thailand 40, 932 sites
Ireland 39, 837 sites
Israel 36, 007 sites
Finland 34, 507 sites
Austria 34, 118 sites
Slovakia 28, 694 sites
Argentina 26, 972 sites
Malaysia 25, 864 sites
Lithuania 24, 714 sites
Belarus 24, 364 sites
Norway 23, 960 sites
Portugal 23, 435 sites
Chile 23, 178 sites
Greece 20, 072 sites
Estonia 17, 846 sites
Kazakstan 14, 891 sites
Slovenia 13, 676 sites
New Zealand 12, 597 sites
Croatia 9, 139 sites
Belize 9, 042 sites
Other Countries
Websites
Live World Websites Statistics
World Websites Database (15, 000, 000+) 15, 229, 296 records
Sites IP Address Change History 62, 391, 102 records
Sites Down/Deleted Domains 4, 102, 985 records
Sites DNS (Nameservers) 1, 115, 626 records
Sites Reverse IP (Hosts) 359, 061 records
Hosting Companies 140, 545 companies
Summary – Websites By Country 252 countries
Report – Hosting Companies140, 545 companies
Report – World Websites15, 229, 296 websites
Other Reports 2020 year »
Blacklist / IP Database
LIVE BLACKLIST STATISTICS
Live IP Addresses Statistics
IPv6 Address Database 4, 349, 588 records
World IP Address Owners (500, 000+) 516, 419 records
Recent IPv6 Addresses Visting Site 3, 069, 272 records
16 Million IP Address Ranges 17, 879, 926 records
IPv6 Ranges by Owner 6, 393 records
IP ASN 48, 208 records
Web Bots 2020 – Web Spider List 6, 004 records
Interesting
Interesting Statistics
Popular Users Statistics
Computer Operating Systems 5, 182 records
Computer Browsers 13, 937 records
Computer Browser Agents 1, 176, 789 records
Countries 253 records
States/Regions 2, 744 records
Cities 245, 432 records
Sitemap
16 Million IP Address Ranges
API Dashboard
API Json / Live Free Sample Queries
About Us
Best Popular Hosting by Country
Bitcoin Price Chart for Your Website
Bitcoin Price History Data
Blacklist Bot/Crawler Types for Websites
Blacklist Ebay Buyers (Live DB)
Blacklist IP Addresses Live Database (Real-time)
Blacklist IPv4/v6 Addresses (User Submitted)
Cities
Computer Browser Agents
Computer Browsers
Computer Operating Systems
Contact Us
Countries
Cryptocurrency – Bitcoin
Files / Reports
Geography
Google, Bing, Yahoo, Facebook, etc – Bot IP Addresses
Google/Yahoo/Bing Bots Last Visit Date
IP
IP ASN
IP Ranges by Owner
IPv4 Address Database
IPv6 Address Database
IPv6 Ranges by Owner
Latest Visitors Statistics Box for Your Website
Major/Biggest IP Address Ranges in the Internet
Premium Services
Products/Reports (2020 year)
Recent IPv4 Addresses Visting Site
Recent IPv6 Addresses Visting Site
Sites DNS (Nameservers)
Sites Down/Deleted Domains
Sites IP Address Change History
Sites Reverse IP (Hosts)
States/Regions
Supporting Tables
Terms and Conditions
Web Bots 2020 – Web Spider List
Whois IPv6 Lookup
Whois Lookup
Whois Regional Internet Registries (RIR)
World Cities SQL/Mysql Database – 2020 year
World Hosting Companies DB (140, 000+)
World IP Address Owners (500, 000+)
World Websites Database (15, 000, 000+)
World Whois Database – Downloadable MySQL Full Version, 2020 year
API
Report for pornhub.com – DNS Inspect
Parent
100
NS
SOA
94
MX
95
Mail
Web
NS Records at Parent Servers
We have successfully fetched domain’s NS records from parent name server ().
Domain NS records:
TTL=172800
[NO GLUE4]
[NO GLUE6]
[156. 154. 140. 3]
[2610:a1:1001::3]
Test ignored, name servers are located outside of current zone.
Name Servers Have A Records
OK.
Found A records for all name servers.
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
Found AAAA records for all name servers.
→ 2620:4d:4000:6259:7:3:0:1
→ 2a00:edc0:6259:7:3::2
→ 2620:4d:4000:6259:7:3:0:3
→ 2a00:edc0:6259:7:3::4
→ 2610:a1:1003::3
→ 2610:a1:1001::3
→ 2610:a1:1002::3
→ 2610:a1:1004::3
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Your name servers returned 8 NS records:
TTL=86400
All Name Servers Responded
All your name servers responded. We queried domain’s records from all of your name servers and we received them successfully.
No differences found.
The glue provided by the parent name servers has to match
the data provided by the authoritative name servers.
Domain name servers are not allowing recursive queries.
On all name servers which acts as caching name servers recursive queries should be restricted to local networks.
Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks.
Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic,
email and other traffic to malicious hosts compromising security.
Domain has 8 name servers. Recommended number,
between 2 and 7 name servers (RFC 2182 recommends to have at
least 3 authoritative name servers for domains).
All your name servers reported identical NS records.
Each name server should return identical NS records.
Check for Lame Name servers
No lame name servers found. All of your name servers are configured to be either master or slave for your domain.
No private IPs found. Name servers using private IPs
can’t be reached from the Internet causing DNS delays.
Found A records for each name servers.
Name Servers Have Valid Names
All names are valid.
Name server name should be a valid host name, no partial name or IP address.
Check for Stealth Name Servers
No stealth name servers found.
All name servers returned by domain name servers should be listed at parent servers.
Check for Missing Name Servers
No missing name servers found.
All name servers returned by the parent name servers should have an NS record at your name servers.
No CNAMEs found in NS records.
RFC 2181, section 10. 3 says that host name must map directly to one or more address record (A or AAAA)
and must not point to any CNAME records.
RFC 1034, section 3. 6. 2 says if a name appears in the right-hand side of RR (Resource Record)
it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with
NS and MX records.
Despite this restrictions, there are many working configuration using CNAME with
All name servers are allowing TCP connections.
When response to a DNS query exceeds 512 bytes, TCP is negotiated
and used, all name servers should allow TCP connections (port 53).
Name Servers Distributed on Multiple Networks
Name servers are dispersed on 6
different C class networks:
156. 0/24:
156. 141. 142. 143. 0/24:
198. 51. 44. 45. 0/24:
Name servers should be dispersed (topologically and geographically)
across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Distributed on Multiple ASNs
Name servers are dispersed on 13
different Autonomous Systems:
AS62597:
AS397213:
AS397215:
AS397218:
AS397220:
AS397224:
AS397228:
AS397231:
AS397232:
AS397233:
AS397235:
AS397238:
AS397242:
Name servers software versions are not exposed:
156. 3: “UltraDNS Resolver”
156. 3: “UltraDNS Resolver”
198. 3: “”
198. 67: “”
198. 67: “”
2610:a1:1001::3: “UltraDNS Resolver”
2610:a1:1002::3: “UltraDNS Resolver”
2610:a1:1003::3: “UltraDNS Resolver”
2610:a1:1004::3: “UltraDNS Resolver”
2620:4d:4000:6259:7:3:0:1: “”
2620:4d:4000:6259:7:3:0:3: “”
2a00:edc0:6259:7:3::2: “”
2a00:edc0:6259:7:3::4: “”
Exposing name server’s versions may be risky, when a new vulnerability is found
your name servers may be automatically exploited by script kiddies
until you patch the system.
Learn how to hide version.
Domain SOA Record:
Primary nameserver:
Hostmaster (e-mail):
Serial: 2014036259
Refresh: 28800
Retry: 7200
Expire: 1209600
Minimum TTL: 43200
Name Servers Agreement on Serial Number
WARNING:
We found different serial numbers on your name servers,
it’s OK if you had modified your zone recently.
156. 3: 2014036259
156. 3: 2014036259
198. 3: 1630434504
198. 67: 1630434504
198. 67: 1630434504
2610:a1:1001::3: 2014036259
2610:a1:1002::3: 2014036259
2610:a1:1003::3: 2014036259
2610:a1:1004::3: 2014036259
2620:4d:4000:6259:7:3:0:1: 1630434504
2620:4d:4000:6259:7:3:0:3: 1630434504
2a00:edc0:6259:7:3::2: 1630434504
2a00:edc0:6259:7:3::4: 1630434504
Having different serials on your name servers may show inconsistencies between name servers
configuration (multiple masters), or communication errors (ACL and firewall issues).
Serial number format OK [2014036259].
Your serial number is following general convention for
serial number YYYYMMDDnn, where YYYY is four-digit year
number, MM is the month, DD is the day and nn is the
sequence number in case zone file is updated more
than once per day.
Primary name server is and is listed at the parent name servers.
The MNAME field defines the Primary Master name server for the zone,
this name server should be found in your NS records.
Contact email for DNS problems is [email protected] ().
RNAME field defines an administrative email for your zone. RFC2142 recommends using hostmaster
e-mail for this purpose, but any valid e-mail address can be used.
Refresh interval is 28800.
Recommended values [1200.. 43200] (20 min… 12 hours).
Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.
Retry interval is 7200.
Recommended values [120.. 7200] (2 minutes.. 2 hours).
Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.
Expire interval is 1209600.
Recommended values [604800.. 1209600] (1 week… 2 weeks).
Expiry defines zone expiration time in seconds after which slave must re-validate zone file,
if contacting master fails then slave will stop responding to any queries.
Minimum TTL value is 43200.
Recommended values [3600.. 86400] (1 hour… 1 day).
Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves
to cache negative responses.
Your name servers returned 2 MX records:
10 TTL=3600
All name servers returned identical MX records.
Mail Servers Have A Records
Found A records for all mail servers.
To reach your mail servers via IPv4 an A record is needed for each mail server.
Mail Servers Have AAAA Records
NOTICE:
While reading domain NS records at parent mail servers,
we found mail servers without AAAA records.
→?
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records
All mail servers have reverse DNS entries configured correctly.
Server
IP
PTR (Reverse)
IPs
67. 231. 158. 156
All mail servers should have a reverse DNS (PTR) entry for
each IP address (RFC 1912). Missing reverse DNS entries will
make many mail servers to reject your e-mails or mark them
as SPAM.
All IP’s reverse DNS entries should resolve back to
IP address (IP → PTR → IP).
Many mail servers are configured to reject e-mails from
IPs with inconsistent reverse DNS configuration.
Check MX Records for Invalid Chars
No invalid characters found.
Name field from MX records should be a valid host name.
Check MX Records IPs are Public
No private IPs found.
Mail servers using private IPs can’t be reached from the Internet causing mail delivery delays.
Check MX Records for Duplicates
MX records duplicates (same IP address):
67. 156: []
Although technically valid, duplicate MX records have no benefits and can cause confusion.
Only Host Names in MX Records
No IPs found in MX records.
IP addresses are not allowed in MX records, only host names.
No CNAMEs found in MX records.
Mail servers IPs are not blacklisted.
Check Google Apps Settings
Test ignored, domain is not using Google Apps.
Successfully connected to all mail servers.
220 ESMTP pe-m0116837
220 ESMTP pe-m0116836
To receive emails, mail servers should allow TCP connections on port 25.
I’ve found differences between mail server host names
and greeting host name. The following mail servers claims
to be other hosts (reverse DNS checks may be wrong):
→
Accepts Postmaster Address
All mail servers are accepting emails to
[email protected] address:
>> MAIL FROM: <[email protected]>
<< 250 2. 1. 0 Sender ok
>> RCPT TO: <[email protected]>
<< 250 2. 5 Recipient ok
RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster.
To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.
Found SPF record:
51v423477tpvn79tnhkc6dcd50vfwsmw
google-site-verification=mBLIe_LYyVmp7-dKcYMnE2VgbHqhMMbF0Ib_lNxydxw
google-site-verification=oiQAl3PbQ5Ozmw2lDDQ_UuJMGvOpEzzJ_b926wxMXcI
v=spf1 mx ip4:94. 199. 255. 10/32 ip4:208. 91. 206. 64/26 ip4:66. 254. 113. 78/32 ip4:66. 119. 174 ip4:66. 78 ip4:66. 112. 72/30 -all
SPF
(Sender Policy Framework) record is designed to prevent e-mail spoofing.
Typical SPF record would be:
v=spf1 a mx ~all
or
v=spf1 a mx ~all if you are using Google Apps.
Name servers returned identical TXT records.
Only SPF records are compared, all name servers should return identical SPF records.
No SPF type records found.
All name servers should return identical SPF records.
Domain resolves to:
66. 114. 41
Domain Name IPs are Public
No private IPs found for
Web servers using private IPs can't be reached from the Internet.
Domain. resolves to:
No private IPs found for Web servers using private IPs can't be reached from the Internet.
Report completed in 1. 40 seconds.
Recent reports:
