visitmidhurst.com - dns.ninja

visitmidhurst.com

DNSSEC⚠️ Not signed
A159.65.55.245🇬🇧 DIGITALOCEAN159.65.48.0/20 DigitalOcean
PTRvisitmidhurst.com
NSns1.digitalocean.com
A2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
A172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
NSns2.digitalocean.com
A2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
A172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
NSns3.digitalocean.com
A2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
A172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
MXaspmx.l.google.com
A2607:f8b0:4004:c21::1b🇺🇸 Google2607:f8b0:4004::/48
PTRpe-in-f27.1e100.net
A172.253.62.26🇺🇸 Google172.253.62.0/24
PTRbc-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1b🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXalt2.aspmx.l.google.com(5)
A2a00:1450:400b:c02::1b🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f27.1e100.net
A172.253.116.26🇺🇸 Google172.253.116.0/24
PTRdj-in-f26.1e100.net
MXalt3.aspmx.l.google.com(10)
A2a00:1450:4009:c0f::1b🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f27.1e100.net
A192.178.223.27🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f27.1e100.net
MXalt4.aspmx.l.google.com(10)
A2a00:1450:400c:c23::1a🇧🇪 Google2a00:1450:400c::/48
PTRyubrupd-in-f26.1e100.net
A172.253.157.26🇺🇸 Google172.253.0.0/16
PTRyubrupd-in-f26.1e100.net
SOAns1.digitalocean.comhostmaster@visitmidhurst.com serial=0

com

WOT: UNKNOWN (62/100)

PTR for

Subdomains

Same first word

DNS History

15 records (9 active, 6 former)

20162017201820192020202120222023202420252026NSns1.digitalocean.comns2.digitalocean.comns3.digitalocean.comns.rackspace.comns2.rackspace.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.commx1.emailsrvr.commx2.emailsrvr.comA159.65.55.245176.9.109.23846.101.25.129
NSns.rackspace.com2015-08-02 → 2015-08-02 · 3 obs
● 2015-08-02 13:32:50
○ 2015-12-01 02:34:12
○ 2026-07-28 22:11:32
NSns1.digitalocean.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
NSns2.digitalocean.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
NSns2.rackspace.com2015-08-02 → 2015-08-02 · 3 obs
● 2015-08-02 13:32:50
○ 2015-12-01 02:34:12
○ 2026-07-28 22:11:32
NSns3.digitalocean.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
MXalt1.aspmx.l.google.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
MXalt2.aspmx.l.google.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
MXalt3.aspmx.l.google.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
MXalt4.aspmx.l.google.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
MXaspmx.l.google.com2015-12-01 → 2026-07-28 · 3 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2026-07-28 22:11:32
MXmx1.emailsrvr.com2015-08-02 → 2015-08-02 · 3 obs
● 2015-08-02 13:32:50
○ 2015-12-01 02:34:12
○ 2026-07-28 22:11:32
MXmx2.emailsrvr.com2015-08-02 → 2015-08-02 · 3 obs
● 2015-08-02 13:32:50
○ 2015-12-01 02:34:12
○ 2026-07-28 22:11:32
A159.65.55.2452026-02-15 → 2026-07-28 · 3 obs
○ 2020-02-29 14:51:44
● 2026-02-15 22:00:06
● 2026-07-28 22:11:32
A176.9.109.2382015-08-02 → 2015-08-02 · 3 obs
● 2015-08-02 13:32:50
○ 2015-12-01 02:34:12
○ 2026-07-28 22:11:32
A46.101.25.1292015-12-01 → 2020-02-29 · 5 obs
○ 2015-08-02 13:32:50
● 2015-12-01 02:34:12
● 2020-02-29 14:51:44
○ 2026-02-15 22:00:06
○ 2026-07-28 22:11:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
visitmidhurst.comns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com3 records

✅ Authoritative Response

Server:172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for visitmidhurst.com (unsigned zone)

⏱️ Timing

Total: 324ms | Queries: -

📄 Records

TypeCountSample Data
A1159.65.55.245
NS3ns2.digitalocean.com, ns1.digitalocean.com...
MX5alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)...
SOA1ns1.digitalocean.com hostmaster.visitmid

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

Hierarchy

visitmidhurst.com serves as the parent of www.visitmidhurst.com.

IP Addresses

visitmidhurst.com has exactly one IP address — 159.65.55.245.

Name Servers

visitmidhurst.com has three name servers — ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

visitmidhurst.com has at least partial name server overlap with other domains, such as mugen.media, boosterhub.com, 58.183.68.in-addr.arpa and two others.

Each of ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com points to two IP numbers. ns1.digitalocean.com points to 172.64.52.210 and 2606:4700:52::ac40:34d2. ns2.digitalocean.com points to 172.64.53.21 and 2606:4700:5a::ac40:3515. ns3.digitalocean.com points to 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

visitmidhurst.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by visitmidhurst.com are shared with other domains: dalkia.co.in, ns500599.ns500737.ns500724.ns500724.ns500599.ns500599.ns500737.ns500697.ns500697.ns500697.ns500682.ns500669.www.yummyflingsfinder.com, ns500671.ns500671.ns500671.ns500705.ns500671.ns500705.ns500688.ns500705.ns500678.ns500666.ns500142.lusty(0x736c7574)z.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com resolves to 172.253.62.26 and 2607:f8b0:4004:c21::1b.

alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.