fetchme.com - dns.ninja

fetchme.com

DNSSEC⚠️ Not signed
NSns1.dns-h.com ⚠️ Not in zone NS records
A129.232.248.31🇿🇦 xneelo129.232.248.0/24 AnyCast DNS
PTRns1.dns-h.com
NSns1.host-h.net ⚠️ Not in zone NS records
A129.232.248.30🇿🇦 xneelo129.232.248.0/24 AnyCast DNS
PTRns1.host-h.net
NSns2.dns-h.com ⚠️ Not in zone NS records
A129.232.248.41🇿🇦 xneelo129.232.248.0/24 AnyCast DNS
PTRns2.dns-h.com
NSns2.host-h.net ⚠️ Not in zone NS records
A129.232.248.40🇿🇦 xneelo129.232.248.0/24 AnyCast DNS
PTRns2.host-h.net

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1783148536

Same first word

fetchme.com
fetchme.co
fetchme.net
fetchme.co.nz

Similar names

femtech.online
femtech.net
femtech.io
meftech.ae
efmtech.com
emftech.com
femtech.or.jp
femtech.com.au
emftech.blogspot.com
techfem.it
femtech.org
fetchem.com
tefchem.com
femtech.co
ftechme.com
femtech.at
fetchem.net
femtech.dk
emftech.net
femtech.com
femtech.health
femtech.kr
techfem.com
mfetech.io
femtech.nl
femtech.ch
femtech.eu

DNS History

19 records (4 active, 15 former)

20162017201820192020202120222023202420252026NSns1.dns-h.comns1.host-h.netns2.dns-h.comns2.host-h.netns1.mywebserver.co.zans1.namefind.comns1.sedoparking.comns2.mywebserver.co.zans2.sedoparking.comns3.mywebserver.co.zaMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.commail.nickstel.comA196.41.127.28208.73.211.7072.52.4.120
●NSns1.dns-h.com2026-04-05 → 2026-07-04 · 3 obs
○ 2017-04-07 05:15:12
● 2026-04-05 16:53:04
● 2026-07-04 07:17:36
●NSns1.host-h.net2026-04-05 → 2026-07-04 · 3 obs
○ 2017-04-07 05:15:12
● 2026-04-05 16:53:04
● 2026-07-04 07:17:36
○NSns1.mywebserver.co.za2017-04-07 → 2017-04-07 · 4 obs
○ 2016-08-08 14:18:24
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○NSns1.namefind.com2015-12-21 → 2016-08-08 · 5 obs
○ 2015-10-21 22:56:10
● 2015-12-21 04:57:18
● 2016-08-08 14:18:24
○ 2017-04-07 05:15:12
○ 2026-07-04 07:17:36
○NSns1.sedoparking.com2015-05-18 → 2015-10-21 · 4 obs
● 2015-05-18 05:13:42
● 2015-10-21 22:56:10
○ 2015-12-21 04:57:18
○ 2026-07-04 07:17:36
●NSns2.dns-h.com2026-04-05 → 2026-07-04 · 3 obs
○ 2017-04-07 05:15:12
● 2026-04-05 16:53:04
● 2026-07-04 07:17:36
●NSns2.host-h.net2026-04-05 → 2026-07-04 · 3 obs
○ 2017-04-07 05:15:12
● 2026-04-05 16:53:04
● 2026-07-04 07:17:36
○NSns2.mywebserver.co.za2017-04-07 → 2017-04-07 · 4 obs
○ 2016-08-08 14:18:24
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○NSns2.sedoparking.com2015-05-18 → 2015-10-21 · 4 obs
● 2015-05-18 05:13:42
● 2015-10-21 22:56:10
○ 2015-12-21 04:57:18
○ 2026-07-04 07:17:36
○NSns3.mywebserver.co.za2017-04-07 → 2017-04-07 · 4 obs
○ 2016-08-08 14:18:24
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○MXalt1.aspmx.l.google.com2017-04-07 → 2017-04-07 · 4 obs
○ 2015-12-21 04:57:18
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○MXalt2.aspmx.l.google.com2017-04-07 → 2017-04-07 · 4 obs
○ 2015-12-21 04:57:18
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○MXalt3.aspmx.l.google.com2017-04-07 → 2017-04-07 · 4 obs
○ 2015-12-21 04:57:18
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○MXalt4.aspmx.l.google.com2017-04-07 → 2017-04-07 · 4 obs
○ 2015-12-21 04:57:18
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○MXaspmx.l.google.com2017-04-07 → 2017-04-07 · 4 obs
○ 2015-12-21 04:57:18
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○MXmail.nickstel.com2015-05-18 → 2015-10-21 · 4 obs
● 2015-05-18 05:13:42
● 2015-10-21 22:56:10
○ 2015-12-21 04:57:18
○ 2026-07-04 07:17:36
○A196.41.127.282017-04-07 → 2017-04-07 · 4 obs
○ 2016-08-08 14:18:24
● 2017-04-07 05:15:12
○ 2026-04-05 16:53:04
○ 2026-07-04 07:17:36
○A208.73.211.702015-12-21 → 2016-08-08 · 5 obs
○ 2015-10-21 22:56:10
● 2015-12-21 04:57:18
● 2016-08-08 14:18:24
○ 2017-04-07 05:15:12
○ 2026-07-04 07:17:36
○A72.52.4.1202015-05-18 → 2015-10-21 · 4 obs
● 2015-05-18 05:13:42
● 2015-10-21 22:56:10
○ 2015-12-21 04:57:18
○ 2026-07-04 07:17:36

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comc.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net...-
fetchme.comns1.host-h.net, ns2.host-h.net, ns1.dns-h.com, ns2.dns-h.com2 records

✅ Authoritative Response

Server:129.232.248.30

NS records: ns1.host-h.net, ns2.host-h.net, ns1.dns-h.com, ns2.dns-h.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fetchme.com (unsigned zone)

⏱️ Timing

Total: 1972ms | Queries: -

📄 Records

TypeCountSample Data

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.dns-h.com, ns2.dns-h.com)

Analysis

Name Servers

The domain fetchme.com is delegated to these four name servers: ns1.dns-h.com, ns2.dns-h.com, ns1.host-h.net and ns2.host-h.net.

The name servers of fetchme.com overlap at least partially with those of other domains — among them shuttleandtours.co.za, enflotech.com, ufhc.co.za and two more.

These name servers commonly appear alongside the name servers ns1a.your-server.co.za and nsa.primary-ns.co.za.

ns1.dns-h.com resolves to 129.232.248.31. ns2.dns-h.com resolves to 129.232.248.41. ns1.host-h.net resolves to 129.232.248.30. ns2.host-h.net resolves to 129.232.248.40. All four hosts carry exactly one IP address.