procurementpidgin.com - dns.ninja
procurementpidgin.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786431169 | ||||||
Same first word
procurementpidgin.com |
DNS History
12 records (9 active, 3 former)
●NSns73.domaincontrol.com2017-05-08 → 2026-08-11 · 2 obs
● 2026-08-11 06:53:40
●NSns74.domaincontrol.com2017-05-08 → 2026-08-11 · 2 obs
● 2026-08-11 06:53:40
●MXalt1.aspmx.l.google.com2026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
●MXalt2.aspmx.l.google.com2026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
●MXaspmx.l.google.com2026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
●MXaspmx2.googlemail.com2026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
●MXaspmx3.googlemail.com2026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
○MXmailstore1.secureserver.net2017-05-08 → 2017-05-08 · 3 obs
○ 2026-03-26 10:42:52
○ 2026-08-11 06:53:40
○MXsmtp.secureserver.net2017-05-08 → 2017-05-08 · 3 obs
○ 2026-03-26 10:42:52
○ 2026-08-11 06:53:40
●A15.197.225.1282026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
●A3.33.251.1682026-03-26 → 2026-08-11 · 3 obs
● 2026-03-26 10:42:52
● 2026-08-11 06:53:40
○A50.63.202.392017-05-08 → 2017-05-08 · 3 obs
○ 2026-03-26 10:42:52
○ 2026-08-11 06:53:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, j.gtld-servers.net... | - |
| procurementpidgin.com | ns73.domaincontrol.com, ns74.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.74.47
NS records: ns73.domaincontrol.com, ns74.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for procurementpidgin.com (unsigned zone)
⏱️ Timing
Total: 263ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns73.domaincontrol.com, ns74.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=ezsQn6ymAeJgqGR, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns73.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns73.domaincontrol.com, ns73.domaincontrol.com, ns74.domaincontrol.com...)
Analysis
IP Addresses
procurementpidgin.com resolves to the IP addresses 3.33.251.168 and 15.197.225.128
Two other host names, along with urban-contractors.com, gpspi.com and harrismckay.com, also share IP numbers with procurementpidgin.com.
Name Servers
procurementpidgin.com has two authoritative name servers — ns73.domaincontrol.com and ns74.domaincontrol.com.
procurementpidgin.com shares its NS records with other domains, for example audiotransitmusic.com, leadsmogul.com, vicentegasco.com and two others.
Both ns73.domaincontrol.com and ns74.domaincontrol.com have two IP addresses each. ns73.domaincontrol.com resolves to 97.74.106.47 and 2603:5:21a4::2f; ns74.domaincontrol.com resolves to 173.201.74.47 and 2603:5:22a4::2f.
Mail Servers
procurementpidgin.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between procurementpidgin.com and other domains, including ns500768.ns500758.ns500758.ns500698.ns500736.ns500735.ns500735.ns500736.ns500708.ns500576.ns500576.ns500708.trackreceptor.com, ns500758.ns500759.ns500758.ns500698.ns500736.ns500698.ns500708.ns500576.ns500615.tracksymphony.com, ns500737.ns500724.ns500724.ns500724.ns500737.ns500737.ns500599.ns500724.ns500697.ns500697.ns500631.www.yummyflingsfinder.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to 172.253.115.27 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.26 IP addresses.