directorypay.com - dns.ninja

directorypay.com

DNSSEC⚠️ Not signed
A34.102.221.37🇺🇸 Google34.100.0.0/14
PTR37.221.102.34.bc.googleusercontent.com
NSns1.uniregistry-dns.com ⚠️ Not in zone NS records
A2a05:d018:e4d:8612:91d7:31de:e607:b526🇮🇪 Amazon2a05:d018:c00::/38 AMAZON AWS
A54.76.92.141🇮🇪 Amazon54.76.0.0/15 EC2 DUB prefix
PTRns1.uniregistry-dns.com
NSns1.uniregistry-dns.net ⚠️ Not in zone NS records
A2a05:d018:e4d:8614:122d:193b:492b:5dd2🇮🇪 Amazon2a05:d018:c00::/38 AMAZON AWS
A52.49.180.240🇮🇪 Amazon52.48.0.0/14 EC2 DUB prefix
PTRns1.uniregistry-dns.net
NSns2.uniregistry-dns.com ⚠️ Not in zone NS records
A2600:1f14:d39:6512:241:9672:68c5:ef64🇺🇸 Amazon2600:1f14:800::/37 AMAZON AWS
A52.26.68.78🇺🇸 Amazon52.24.0.0/14 EC2 PDX prefix
PTRns2.uniregistry-dns.com
NSns2.uniregistry-dns.net ⚠️ Not in zone NS records
A2600:1f14:d39:6514:94ab:114f:8599:b36🇺🇸 Amazon2600:1f14:800::/37 AMAZON AWS
A52.38.7.42🇺🇸 Amazon52.36.0.0/14 EC2 PDX prefix
PTRns2.uniregistry-dns.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=1783184466

Same first word

directorypay.xyz
directorypay.com

DNS History

29 records (5 active, 24 former)

200920112013201520172019202120232025NSns1.uniregistry-dns.comns1.uniregistry-dns.netns2.uniregistry-dns.comns2.uniregistry-dns.netns1.fabulous.comns1.namebrightdns.comns2.fabulous.comns2.namebrightdns.comnsg1.namebrightdns.comnsg2.namebrightdns.comMXanmail.namebrightmail.compostbox.fabulous.comA34.102.221.37107.23.198.240216.34.131.13552.200.243.12352.206.43.23452.4.72.13754.152.144.24354.174.31.25454.208.74.21554.209.90.8154.210.33.19054.236.123.22454.84.53.3854.85.54.2954.88.107.140CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.comhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com
○NSns1.fabulous.com2008-03-07 → 2008-03-07 · 3 obs
● 2008-03-07 22:05:04
○ 2015-06-19 13:04:24
○ 2026-07-04 17:23:54
○NSns1.namebrightdns.com2015-06-19 → 2017-12-15 · 8 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
● 2016-01-20 09:43:00
○ 2016-04-09 09:43:22
● 2016-09-17 19:20:30
● 2017-12-15 06:42:06
○ 2026-03-05 20:26:16
○ 2026-07-04 17:23:54
●NSns1.uniregistry-dns.com2026-03-05 → 2026-07-04 · 3 obs
○ 2017-12-15 06:42:06
● 2026-03-05 20:26:16
● 2026-07-04 17:23:54
●NSns1.uniregistry-dns.net2026-03-05 → 2026-07-04 · 3 obs
○ 2017-12-15 06:42:06
● 2026-03-05 20:26:16
● 2026-07-04 17:23:54
○NSns2.fabulous.com2008-03-07 → 2008-03-07 · 3 obs
● 2008-03-07 22:05:04
○ 2015-06-19 13:04:24
○ 2026-07-04 17:23:54
○NSns2.namebrightdns.com2015-06-19 → 2017-12-15 · 7 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
○ 2015-10-30 03:47:36
● 2016-01-20 09:43:00
● 2017-12-15 06:42:06
○ 2026-03-05 20:26:16
○ 2026-07-04 17:23:54
●NSns2.uniregistry-dns.com2026-03-05 → 2026-07-04 · 3 obs
○ 2017-12-15 06:42:06
● 2026-03-05 20:26:16
● 2026-07-04 17:23:54
●NSns2.uniregistry-dns.net2026-03-05 → 2026-07-04 · 3 obs
○ 2017-12-15 06:42:06
● 2026-03-05 20:26:16
● 2026-07-04 17:23:54
○NSnsg1.namebrightdns.com2015-06-19 → 2015-10-30 · 5 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
● 2015-10-30 03:47:36
○ 2016-01-20 09:43:00
○ 2026-07-04 17:23:54
○NSnsg2.namebrightdns.com2015-10-30 → 2016-04-09 · 6 obs
○ 2015-06-19 13:04:24
● 2015-10-30 03:47:36
○ 2016-01-20 09:43:00
● 2016-04-09 09:43:22
○ 2016-09-17 19:20:30
○ 2026-07-04 17:23:54
○MXanmail.namebrightmail.com2015-06-19 → 2015-06-19 · 4 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
○ 2015-10-30 03:47:36
○ 2026-07-04 17:23:54
○MXpostbox.fabulous.com2008-03-07 → 2008-03-07 · 3 obs
● 2008-03-07 22:05:04
○ 2015-06-19 13:04:24
○ 2026-07-04 17:23:54
○A107.23.198.2402016-09-17 → 2016-09-17 · 4 obs
○ 2016-04-09 09:43:22
● 2016-09-17 19:20:30
○ 2016-12-30 09:52:36
○ 2026-07-04 17:23:54
○A216.34.131.1352008-03-07 → 2008-03-07 · 3 obs
● 2008-03-07 22:05:04
○ 2015-06-19 13:04:24
○ 2026-07-04 17:23:54
●A34.102.221.372026-03-05 → 2026-07-04 · 3 obs
○ 2017-12-15 06:42:06
● 2026-03-05 20:26:16
● 2026-07-04 17:23:54
○A52.200.243.1232016-04-09 → 2016-04-09 · 4 obs
○ 2016-01-20 09:43:00
● 2016-04-09 09:43:22
○ 2016-09-17 19:20:30
○ 2026-07-04 17:23:54
○A52.206.43.2342016-09-17 → 2016-09-17 · 4 obs
○ 2016-04-09 09:43:22
● 2016-09-17 19:20:30
○ 2016-12-30 09:52:36
○ 2026-07-04 17:23:54
○A52.4.72.1372016-09-17 → 2016-09-17 · 4 obs
○ 2016-04-09 09:43:22
● 2016-09-17 19:20:30
○ 2016-12-30 09:52:36
○ 2026-07-04 17:23:54
○A54.152.144.2432016-04-09 → 2016-04-09 · 4 obs
○ 2016-01-20 09:43:00
● 2016-04-09 09:43:22
○ 2016-09-17 19:20:30
○ 2026-07-04 17:23:54
○A54.174.31.2542015-06-19 → 2015-10-30 · 5 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
● 2015-10-30 03:47:36
○ 2016-01-20 09:43:00
○ 2026-07-04 17:23:54
○A54.208.74.2152015-06-19 → 2015-10-30 · 5 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
● 2015-10-30 03:47:36
○ 2016-01-20 09:43:00
○ 2026-07-04 17:23:54
○A54.209.90.812016-01-20 → 2016-01-20 · 4 obs
○ 2015-10-30 03:47:36
● 2016-01-20 09:43:00
○ 2016-04-09 09:43:22
○ 2026-07-04 17:23:54
○A54.210.33.1902016-09-17 → 2016-09-17 · 4 obs
○ 2016-04-09 09:43:22
● 2016-09-17 19:20:30
○ 2016-12-30 09:52:36
○ 2026-07-04 17:23:54
○A54.236.123.2242016-09-17 → 2016-09-17 · 4 obs
○ 2016-04-09 09:43:22
● 2016-09-17 19:20:30
○ 2016-12-30 09:52:36
○ 2026-07-04 17:23:54
○A54.84.53.382016-12-30 → 2016-12-30 · 4 obs
○ 2016-09-17 19:20:30
● 2016-12-30 09:52:36
○ 2017-12-15 06:42:06
○ 2026-07-04 17:23:54
○A54.85.54.292016-01-20 → 2016-01-20 · 4 obs
○ 2015-10-30 03:47:36
● 2016-01-20 09:43:00
○ 2016-04-09 09:43:22
○ 2026-07-04 17:23:54
○A54.88.107.1402016-12-30 → 2016-12-30 · 4 obs
○ 2016-09-17 19:20:30
● 2016-12-30 09:52:36
○ 2017-12-15 06:42:06
○ 2026-07-04 17:23:54
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-06-19 → 2016-09-17 · 5 obs
○ 2008-03-07 22:05:04
● 2015-06-19 13:04:24
● 2016-09-17 19:20:30
○ 2016-12-30 09:52:36
○ 2026-07-04 17:23:54
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2016-12-30 → 2017-12-15 · 5 obs
○ 2016-09-17 19:20:30
● 2016-12-30 09:52:36
● 2017-12-15 06:42:06
○ 2026-03-05 20:26:16
○ 2026-07-04 17:23:54

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comm.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net...-
directorypay.comns1.uniregistry-dns.com, ns2.uniregistry-dns.com, ns1.uniregistry-dns.net, ns2.uniregistry-dns.net4 records

✅ Authoritative Response

Server:52.26.68.78

NS records: ns1.uniregistry-dns.com, ns2.uniregistry-dns.com, ns1.uniregistry-dns.net, ns2.uniregistry-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for directorypay.com (unsigned zone)

⏱️ Timing

Total: 597ms | Queries: -

📄 Records

TypeCountSample Data
A134.102.221.37

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.uniregistry-dns.com, ns1.uniregistry-dns.com, ns2.uniregistry-dns.com...)

Analysis

IP Addresses

directorypay.com resolves to just one IP address, 34.102.221.37.

Two other host names, along with cert.www.stockhawk.net, veqto.com and blackrockleasing.com, also share IP numbers with directorypay.com.

Name Servers

The NS records for directorypay.com point to four name servers: ns1.uniregistry-dns.com, ns2.uniregistry-dns.com, ns1.uniregistry-dns.net and ns2.uniregistry-dns.net.

directorypay.com shares at least some of its name servers with other domains, including uni.dating, diologic.com, kasyno.casino and two others.

The host names ns1.uniregistry-dns.com, ns2.uniregistry-dns.com, ns1.uniregistry-dns.net and ns2.uniregistry-dns.net each resolve to two IP addresses: ns1.uniregistry-dns.com resolves to 54.76.92.141 and 2a05:d018:e4d:8612:91d7:31de:e607:b526; ns2.uniregistry-dns.com resolves to 52.26.68.78 and 2600:1f14:d39:6512:241:9672:68c5:ef64; ns1.uniregistry-dns.net resolves to 52.49.180.240 and 2a05:d018:e4d:8614:122d:193b:492b:5dd2; ns2.uniregistry-dns.net resolves to 52.38.7.42 and 2600:1f14:d39:6514:94ab:114f:8599:b36.