justmetalcard.com - robtex.com
justmetalcard.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=1786228244 | ||||||
Same first word
justmetalcard.com |
DNS History
11 records (7 active, 4 former)
●NSchad.ns.cloudflare.com2026-05-06 → 2026-08-08 · 3 obs
● 2026-05-06 23:21:32
● 2026-08-08 22:59:32
●NSdaisy.ns.cloudflare.com2026-05-06 → 2026-08-08 · 3 obs
● 2026-05-06 23:21:32
● 2026-08-08 22:59:32
○NSns1.dnsowl.com2019-12-16 → 2021-03-04 · 4 obs
● 2021-03-04 21:35:32
○ 2026-05-06 23:21:32
○ 2026-08-08 22:59:32
○NSns2.dnsowl.com2019-12-16 → 2021-03-04 · 4 obs
● 2021-03-04 21:35:32
○ 2026-05-06 23:21:32
○ 2026-08-08 22:59:32
○NSns3.dnsowl.com2019-12-16 → 2021-03-04 · 4 obs
● 2021-03-04 21:35:32
○ 2026-05-06 23:21:32
○ 2026-08-08 22:59:32
●MXalt1.aspmx.l.google.com2026-05-06 → 2026-08-08 · 2 obs
● 2026-08-08 22:59:32
●MXalt2.aspmx.l.google.com2026-05-06 → 2026-08-08 · 2 obs
● 2026-08-08 22:59:32
●MXalt3.aspmx.l.google.com2026-05-06 → 2026-08-08 · 2 obs
● 2026-08-08 22:59:32
●MXalt4.aspmx.l.google.com2026-05-06 → 2026-08-08 · 2 obs
● 2026-08-08 22:59:32
○A35.231.132.2022019-12-16 → 2021-03-04 · 4 obs
● 2021-03-04 21:35:32
○ 2026-05-06 23:21:32
○ 2026-08-08 22:59:32
●A89.117.20.162026-05-06 → 2026-08-08 · 3 obs
● 2026-05-06 23:21:32
● 2026-08-08 22:59:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| justmetalcard.com | daisy.ns.cloudflare.com, chad.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.82
NS records: daisy.ns.cloudflare.com, chad.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for justmetalcard.com (unsigned zone)
⏱️ Timing
Total: 291ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 89.117.20.16 |
| NS | 2 | chad.ns.cloudflare.com, daisy.ns.cloudflare.com |
| MX | 4 | alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=-dAQJNHfZtpC4vZ, v=spf1 ip4:209.126.125.51 include:szsuno |
| SOA | 1 | chad.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (daisy.ns.cloudflare.com, daisy.ns.cloudflare.com, daisy.ns.cloudflare.com...)
Analysis
IP Addresses
justmetalcard.com has exactly one IP address — 89.117.20.16.
Other hosts including myvapepack.com, metalcreditkard.com and vmi2306537.contaboserver.net share IP addresses with justmetalcard.com.
Name Servers
The NS records for justmetalcard.com delegate to chad.ns.cloudflare.com and daisy.ns.cloudflare.com.
The name server configuration of justmetalcard.com is shared with other domains, for instance xem(0x736578)z.xyz, lakridsbybulow.dk, lolaer.com and two others.
There is at least partial name server overlap between justmetalcard.com and other domains — radacina.xyz, plumoy.com, connectpm.com.au and two more among them.
The name servers nina.ns.cloudflare.com, alec.ns.cloudflare.com and betty.ns.cloudflare.com are often found in combination with these name servers.
Hosts with 6 IP addresses each:
chad.ns.cloudflare.com maps to 108.162.193.82, 172.64.33.82, 173.245.59.82 and 3 additional IP addresses.
daisy.ns.cloudflare.com maps to 108.162.192.90, 172.64.32.90, 173.245.58.90 and 3 additional IP addresses.
Mail Servers
The four mail servers for justmetalcard.com are alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
At least some of the mail servers used by justmetalcard.com are shared with other domains: artemleaders.com, ns500758.ns500758.ns500758.ns500758.ns500698.ns500735.ns500698.ns500735.ns500735.ns500576.ns500576.ns500698.ns500686.ns500652.ns500619.trackreceptor.com, ns500765.ns500693.ns500693.ns500693.ns500693.ns500693.ns500693.ns500699.ns500699.ns500699.ns500588.ns500588.ns500588.ns500588.ns500110.dtrkdll.com and two others among them.
It is common to find these mail servers paired with the mail servers aspmx.l.google.com, aspmx3.googlemail.com and aspmx2.googlemail.com, as well as two others.
All four hostnames — alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com — resolve to two IP numbers apiece: alt1.aspmx.l.google.com to 108.177.123.27 and 2800:3f0:4003:c0f::1a; alt2.aspmx.l.google.com to 172.253.116.26 and 2a00:1450:400b:c02::1a; alt3.aspmx.l.google.com to 192.178.223.27 and 2a00:1450:4009:c0f::1b; alt4.aspmx.l.google.com to 172.253.157.26 and 2a00:1450:400c:c23::1b.