boysdateforfree.com - robtex.com
boysdateforfree.com
com
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a.gtld-servers.net β | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786406899 | ||||||
Same first word
boysdateforfree.com |
DNS History
9 records (8 active, 1 former)
βNSns1.netnames.net2015-08-22 β 2026-08-11 Β· 2 obs
β 2026-08-11 00:28:10
βNSns2.netnames.net2015-08-22 β 2026-08-11 Β· 2 obs
β 2026-08-11 00:28:10
βNSns5.netnames.net2015-08-22 β 2026-08-11 Β· 2 obs
β 2026-08-11 00:28:10
βNSns6.netnames.net2015-08-22 β 2026-08-11 Β· 2 obs
β 2026-08-11 00:28:10
βMXrelay1.netnames.net2015-08-22 β 2026-08-11 Β· 2 obs
β 2026-08-11 00:28:10
βMXrelay2.netnames.net2015-08-22 β 2026-08-11 Β· 2 obs
β 2026-08-11 00:28:10
βA165.160.13.202026-02-28 β 2026-08-11 Β· 3 obs
β 2026-02-28 15:33:38
β 2026-08-11 00:28:10
βA165.160.15.202026-02-28 β 2026-08-11 Β· 3 obs
β 2026-02-28 15:33:38
β 2026-08-11 00:28:10
βA185.26.230.1292015-08-22 β 2017-05-21 Β· 4 obs
β 2017-05-21 19:21:30
β 2026-02-28 15:33:38
β 2026-08-11 00:28:10
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net... | - |
| boysdateforfree.com | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | - |
β Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for boysdateforfree.com (unsigned zone)
β±οΈ Timing
Total: 656ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.15.20, 165.160.13.20 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
Analysis
IP Addresses
boysdateforfree.com has two IP addresses: 165.160.13.20 and 165.160.15.20
Among the host names that share IP numbers with boysdateforfree.com are dita.jp, natixis.site, trysharkpowerhead.com and two others.
Name Servers
The domain boysdateforfree.com is delegated to these four name servers: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
The name servers of boysdateforfree.com overlap at least partially with those of other domains β among them tesa.in, intpet.com.ar, ashmoreclients.com and two more.
These name servers commonly appear alongside the name servers ns7.netnames.net and ns8.netnames.net.
Each of ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net resolves to two IP numbers, falling into two groups: ns1.netnames.net and ns5.netnames.net share 156.154.130.100 and 2610:a1:1022::100, while ns2.netnames.net and ns6.netnames.net share 156.154.131.100 and 2610:a1:1023::100.
Both ns1.netnames.net and ns5.netnames.net resolve to 2610:a1:1022::100 IP addresses each.
Both ns1.netnames.net and ns5.netnames.net resolve to 156.154.130.100 IP addresses each.
Both ns2.netnames.net and ns6.netnames.net resolve to 2610:a1:1023::100 IP addresses each.
Both ns2.netnames.net and ns6.netnames.net resolve to 156.154.131.100 IP addresses each.
Mail Servers
The MX records for boysdateforfree.com point to two mail servers: relay1.netnames.net and relay2.netnames.net.
boysdateforfree.com has the same mail server arrangement as a number of other domains, for example aspeninsuranceuk.ltd, intellicad.pt, hoovercandy.eu and two more.
boysdateforfree.com has mail servers in common with other domains β poits.net being one example.
Both relay1.netnames.net and relay2.netnames.net have a single IP address each β relay1.netnames.net resolves to 185.26.230.83 while relay2.netnames.net resolves to 185.26.230.89.