runcorpe.com - dns.ninja

runcorpe.com

com

Same first word

Similar names

DNS History

11 records (5 active, 6 former)

2017201820192020202120222023202420252026NSns-cloud-d1.googledomains.comns-cloud-d2.googledomains.comns-cloud-d3.googledomains.comns-cloud-d4.googledomains.comns53.domaincontrol.comns54.domaincontrol.comMXmail.runcorpe.commailstore1.secureserver.netsmtp.secureserver.netA35.232.30.59107.180.12.39
●NSns-cloud-d1.googledomains.com2026-02-14 β†’ 2026-07-10 Β· 3 obs
β—‹ 2017-09-27 00:31:16
● 2026-02-14 19:12:52
● 2026-07-10 20:45:28
●NSns-cloud-d2.googledomains.com2026-02-14 β†’ 2026-07-10 Β· 3 obs
β—‹ 2017-09-27 00:31:16
● 2026-02-14 19:12:52
● 2026-07-10 20:45:28
●NSns-cloud-d3.googledomains.com2026-02-14 β†’ 2026-07-10 Β· 3 obs
β—‹ 2017-09-27 00:31:16
● 2026-02-14 19:12:52
● 2026-07-10 20:45:28
●NSns-cloud-d4.googledomains.com2026-02-14 β†’ 2026-07-10 Β· 3 obs
β—‹ 2017-09-27 00:31:16
● 2026-02-14 19:12:52
● 2026-07-10 20:45:28
β—‹NSns53.domaincontrol.com2016-12-17 β†’ 2017-09-27 Β· 4 obs
● 2016-12-17 02:56:14
● 2017-09-27 00:31:16
β—‹ 2026-02-14 19:12:52
β—‹ 2026-07-10 20:45:28
β—‹NSns54.domaincontrol.com2016-12-17 β†’ 2017-09-27 Β· 4 obs
● 2016-12-17 02:56:14
● 2017-09-27 00:31:16
β—‹ 2026-02-14 19:12:52
β—‹ 2026-07-10 20:45:28
β—‹MXmail.runcorpe.com2016-12-17 β†’ 2026-02-14 Β· 4 obs
● 2016-12-17 02:56:14
● 2026-02-14 19:12:52
β—‹ 2026-03-23 22:31:40
β—‹ 2026-07-10 20:45:28
β—‹MXmailstore1.secureserver.net2016-12-17 β†’ 2026-02-14 Β· 4 obs
● 2016-12-17 02:56:14
● 2026-02-14 19:12:52
β—‹ 2026-03-23 22:31:40
β—‹ 2026-07-10 20:45:28
β—‹MXsmtp.secureserver.net2016-12-17 β†’ 2026-02-14 Β· 4 obs
● 2016-12-17 02:56:14
● 2026-02-14 19:12:52
β—‹ 2026-03-23 22:31:40
β—‹ 2026-07-10 20:45:28
β—‹A107.180.12.392016-12-17 β†’ 2017-09-27 Β· 4 obs
● 2016-12-17 02:56:14
● 2017-09-27 00:31:16
β—‹ 2026-02-14 19:12:52
β—‹ 2026-07-10 20:45:28
●A35.232.30.592026-02-14 β†’ 2026-07-10 Β· 3 obs
β—‹ 2017-09-27 00:31:16
● 2026-02-14 19:12:52
● 2026-07-10 20:45:28

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comb.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net...-
runcorpe.comns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com8 records

βœ… Authoritative Response

Server:216.239.32.109

NS records: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for runcorpe.com (unsigned zone)

⏱️ Timing

Total: 674ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A135.232.30.59
NS4ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com...
SOA1ns-cloud-d1.googledomains.com cloud-dns-

πŸ“Œ Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-d1.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com...)

Analysis

IP Addresses

runcorpe.com directs to one IP number, which is 35.232.30.59.

Host names like 59.30.232.35.bc.googleusercontent.com are further examples that share IP numbers with runcorpe.com.

Name Servers

The domain runcorpe.com is delegated to these four name servers: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.

runcorpe.com has at least partial name server overlap with other domains, such as brickcode.com, renolds.com, glamvie.com and two others.

ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com all point to exactly two IP numbers each: ns-cloud-d1.googledomains.com β†’ 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com β†’ 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com β†’ 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com β†’ 216.239.38.109 and 2001:4860:4802:38::6d.