quickmedcards.com - dns.ninja
quickmedcards.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=1785207537 | ||||||
Same first word
quickmedcards.com |
DNS History
13 records (9 active, 4 former)
●NSns1.dnsowl.com2018-06-12 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●NSns2.dnsowl.com2018-06-12 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●NSns3.dnsowl.com2018-06-12 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●MXalt1.aspmx.l.google.com2021-02-18 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●MXalt2.aspmx.l.google.com2021-02-18 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●MXalt3.aspmx.l.google.com2021-02-18 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●MXalt4.aspmx.l.google.com2021-02-18 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
●MXaspmx.l.google.com2021-02-18 → 2026-07-28 · 2 obs
● 2026-07-28 03:27:28
○A107.161.23.2042018-06-12 → 2018-06-12 · 3 obs
○ 2021-02-18 19:30:56
○ 2026-07-28 03:27:28
○A192.161.187.2002018-06-12 → 2018-06-12 · 3 obs
○ 2021-02-18 19:30:56
○ 2026-07-28 03:27:28
○A209.141.38.712018-06-12 → 2018-06-12 · 3 obs
○ 2021-02-18 19:30:56
○ 2026-07-28 03:27:28
○A34.218.199.2432021-02-18 → 2021-02-18 · 4 obs
● 2021-02-18 19:30:56
○ 2026-03-17 03:35:02
○ 2026-07-28 03:27:28
●A52.12.166.42026-03-17 → 2026-07-28 · 3 obs
● 2026-03-17 03:35:02
● 2026-07-28 03:27:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| quickmedcards.com | ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com | 12 records |
✅ Authoritative Response
Server:162.159.26.234
NS records: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for quickmedcards.com (unsigned zone)
⏱️ Timing
Total: 326ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.12.166.4 |
| NS | 3 | ns1.dnsowl.com, ns2.dnsowl.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | google-site-verification=CdMV50fTQBsc0rR, google-site-verification=WsUmHemAZRc_6GB... |
| SOA | 1 | ns1.dnsowl.com hostmaster.dnsowl.com |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ns1.dnsowl.com, ns1.dnsowl.com, ns1.dnsowl.com...)
Analysis
IP Addresses
quickmedcards.com resolves to just one IP address, 52.12.166.4.
Host names such as shaco.club, ec2-52-12-166-4.us-west-2.compute.amazonaws.com and protuit.com share their IP numbers with quickmedcards.com.
Name Servers
quickmedcards.com carries NS records delegating to ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.
The name servers of quickmedcards.com overlap at least partially with those of other domains — among them pin-up-casino-sztg3.top, funrape.com, printual.com and two more.
The hosts ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com each resolve to four IP addresses. ns1.dnsowl.com points to 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88 and 2400:cb00:2049:1::a29f:1bad. ns2.dnsowl.com points to 162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31 and 2400:cb00:2049:1::a29f:1b82. ns3.dnsowl.com points to 162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea and 2400:cb00:2049:1::a29f:1b62.
Mail Servers
Five mail servers handle quickmedcards.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between quickmedcards.com and other domains, including kenall.oc.dev, ns500737.ns500599.ns500737.ns500737.ns500737.ns500599.ns500737.ns500737.ns500724.ns500599.ns500583.ns500697.ns500697.ns500631.www.yummyflingsfinder.com, keyringinc.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to two addresses: 64.233.180.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.