214.com - robtex.com

214.com

DNSSEC⚠️ Not signed
NSns1.google.com ⚠️ Not in zone NS records
A2001:4860:4802:32::aπŸ‡ΊπŸ‡Έ Google2001:4860::/32
PTRns1.google.com
A216.239.32.10πŸ‡ΊπŸ‡Έ Google216.239.32.0/24
PTRns1.google.com
NSns2.google.com ⚠️ Not in zone NS records
A2001:4860:4802:34::aπŸ‡ΊπŸ‡Έ Google2001:4860::/32
PTRns2.google.com
A216.239.34.10πŸ‡ΊπŸ‡Έ Google216.239.34.0/24
PTRns2.google.com
NSns3.google.com ⚠️ Not in zone NS records
A2001:4860:4802:36::aπŸ‡ΊπŸ‡Έ Google2001:4860::/32
PTRns3.google.com
A216.239.36.10πŸ‡ΊπŸ‡Έ Google216.239.36.0/24
PTRns3.google.com
NSns4.google.com ⚠️ Not in zone NS records
A2001:4860:4802:38::aπŸ‡ΊπŸ‡Έ Google2001:4860::/32
PTRns4.google.com
A216.239.38.10πŸ‡ΊπŸ‡Έ Google216.239.38.0/24
PTRns4.google.com

com

WOT: SAFE (1/100)

Same first word

Similar names

DNS History

10 records (4 active, 6 former)

20162017201820192020202120222023202420252026NSns1.google.comns2.google.comns3.google.comns4.google.comdns1.iidns.comdns2.iidns.comdns3.iidns.comdns4.iidns.comdns5.iidns.comdns6.iidns.com
β—‹NSdns1.iidns.com2015-08-17 β†’ 2017-02-15 Β· 4 obs
● 2015-08-17 00:44:40
● 2017-02-15 00:36:28
β—‹ 2026-04-01 07:53:04
β—‹ 2026-07-22 15:30:58
β—‹NSdns2.iidns.com2015-08-17 β†’ 2017-02-15 Β· 4 obs
● 2015-08-17 00:44:40
● 2017-02-15 00:36:28
β—‹ 2026-04-01 07:53:04
β—‹ 2026-07-22 15:30:58
β—‹NSdns3.iidns.com2015-08-17 β†’ 2017-02-15 Β· 4 obs
● 2015-08-17 00:44:40
● 2017-02-15 00:36:28
β—‹ 2026-04-01 07:53:04
β—‹ 2026-07-22 15:30:58
β—‹NSdns4.iidns.com2015-08-17 β†’ 2017-02-15 Β· 4 obs
● 2015-08-17 00:44:40
● 2017-02-15 00:36:28
β—‹ 2026-04-01 07:53:04
β—‹ 2026-07-22 15:30:58
β—‹NSdns5.iidns.com2015-08-17 β†’ 2017-02-15 Β· 4 obs
● 2015-08-17 00:44:40
● 2017-02-15 00:36:28
β—‹ 2026-04-01 07:53:04
β—‹ 2026-07-22 15:30:58
β—‹NSdns6.iidns.com2015-08-17 β†’ 2017-02-15 Β· 4 obs
● 2015-08-17 00:44:40
● 2017-02-15 00:36:28
β—‹ 2026-04-01 07:53:04
β—‹ 2026-07-22 15:30:58
●NSns1.google.com2026-04-01 β†’ 2026-07-22 Β· 3 obs
β—‹ 2017-02-15 00:36:28
● 2026-04-01 07:53:04
● 2026-07-22 15:30:58
●NSns2.google.com2026-04-01 β†’ 2026-07-22 Β· 3 obs
β—‹ 2017-02-15 00:36:28
● 2026-04-01 07:53:04
● 2026-07-22 15:30:58
●NSns3.google.com2026-04-01 β†’ 2026-07-22 Β· 3 obs
β—‹ 2017-02-15 00:36:28
● 2026-04-01 07:53:04
● 2026-07-22 15:30:58
●NSns4.google.com2026-04-01 β†’ 2026-07-22 Β· 3 obs
β—‹ 2017-02-15 00:36:28
● 2026-04-01 07:53:04
● 2026-07-22 15:30:58

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comd.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net...-
214.comns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com8 records

βœ… Authoritative Response

Server:216.239.34.10

NS records: ns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 214.com (unsigned zone)

⏱️ Timing

Total: 1297ms | Queries: -

πŸ“„ Records

TypeCountSample Data

πŸ“Œ Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns2.google.com, ns2.google.com, ns1.google.com...)

Analysis

Name Servers

The NS records for 214.com point to four name servers: ns1.google.com, ns2.google.com, ns3.google.com and ns4.google.com.

214.com has at least partial name server overlap with other domains, such as financialleadonline.com, brewedbeans.money, goog.gl and two others.

ns1.google.com, ns2.google.com, ns3.google.com and ns4.google.com all point to exactly two IP numbers each: ns1.google.com β†’ 216.239.32.10 and 2001:4860:4802:32::a; ns2.google.com β†’ 216.239.34.10 and 2001:4860:4802:34::a; ns3.google.com β†’ 216.239.36.10 and 2001:4860:4802:36::a; ns4.google.com β†’ 216.239.38.10 and 2001:4860:4802:38::a.