why203k.com - robtex.com

Search for stuff

why203k.com

DNSSEC⚠️ Not signed
A13.32.241.29🇺🇸 Amazon
PTRserver-13-32-241-29.jfk50.r.cloudfront.net
A13.32.241.41🇺🇸 Amazon
A13.32.241.49🇺🇸 Amazon
A13.32.241.95🇺🇸 Amazon
NSns-1926.awsdns-48.co.uk ⭐
A2600:9000:5307:8600::1🇺🇸 Amazon
PTRns-1926.awsdns-48.co.uk
A205.251.199.134🇺🇸 Amazon
PTRns-1926.awsdns-48.co.uk
NSns-1033.awsdns-01.org
A2600:9000:5304:900::1🇺🇸 Amazon
PTRns-1033.awsdns-01.org
A205.251.196.9🇺🇸 Amazon
PTRns-1033.awsdns-01.org
NSns-21.awsdns-02.com
A2600:9000:5300:1500::1🇺🇸 Amazon
PTRns-21.awsdns-02.com
A205.251.192.21🇺🇸 Amazon
PTRns-21.awsdns-02.com
NSns-917.awsdns-50.net
A2600:9000:5303:9500::1🇺🇸 Amazon
PTRns-917.awsdns-50.net
A205.251.195.149🇺🇸 Amazon
PTRns-917.awsdns-50.net
MXalt1.aspmx.l.google.com(999)
A2607:f8b0:4003:c30::1b🇺🇸 Google
PTRyutulis-in-f27.1e100.net
A74.125.27.27🇺🇸 Google
PTRyutulis-in-f27.1e100.net
MXalt2.aspmx.l.google.com(999)
A2607:f8b0:4001:c70::1a🇺🇸 Google
PTRyucbful-in-f26.1e100.net
A192.178.209.27🇺🇸 Google
PTRyucbful-in-f27.1e100.net
MXalt3.aspmx.l.google.com(999)
A2607:f8b0:4024:c0d::1a🇺🇸 Google
PTRmj-in-f26.1e100.net
A192.178.152.27🇺🇸 Google
PTRmj-in-f27.1e100.net
MXalt4.aspmx.l.google.com(999)
A2607:f8b0:4023:403::1a🇺🇸 Google
PTRgg-in-f26.1e100.net
A142.250.96.27🇺🇸 Google
PTRgg-in-f27.1e100.net
MXaspmx.l.google.com(999)
A2a00:1450:4009:c0f::1a🇬🇧 Google
PTRyulhrs-in-f26.1e100.net
A192.178.223.26🇺🇸 Google
PTRyulhrs-in-f26.1e100.net
SOAns-1926.awsdns-48.co.ukawsdns-hostmaster@amazon.com serial=1

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=1770918430

Same first word

why203k.com

DNS History

26 records (13 active, 13 former)

20162017201820192020202120222023202420252026NSns-1033.awsdns-01.orgns-1926.awsdns-48.co.ukns-21.awsdns-02.comns-917.awsdns-50.netns1.go-mol.comns3.go-mol.comns4.go-mol.comns5.go-mol.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comwhy203k.com.s5a1.psmtp.comwhy203k.com.s5a2.psmtp.comwhy203k.com.s5b1.psmtp.comwhy203k.com.s5b2.psmtp.comA13.32.241.2913.32.241.4113.32.241.4913.32.241.9513.226.238.12813.226.238.2213.226.238.7913.226.238.8069.89.86.145
●NSns-1033.awsdns-01.org2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●NSns-1926.awsdns-48.co.uk2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●NSns-21.awsdns-02.com2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●NSns-917.awsdns-50.net2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
○NSns1.go-mol.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○NSns3.go-mol.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○NSns4.go-mol.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○NSns5.go-mol.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
●MXalt1.aspmx.l.google.com2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●MXalt2.aspmx.l.google.com2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●MXalt3.aspmx.l.google.com2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●MXalt4.aspmx.l.google.com2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
●MXaspmx.l.google.com2018-07-11 → 2026-02-15 · 3 obs
○ 2017-01-29 22:42:32
● 2018-07-11 00:07:02
● 2026-02-15 19:13:30
○MXwhy203k.com.s5a1.psmtp.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○MXwhy203k.com.s5a2.psmtp.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○MXwhy203k.com.s5b1.psmtp.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○MXwhy203k.com.s5b2.psmtp.com2015-07-14 → 2017-01-29 · 4 obs
● 2015-07-14 11:05:14
● 2017-01-29 22:42:32
○ 2018-07-11 00:07:02
○ 2026-02-15 19:13:30
○A13.226.238.1282026-02-14 → 2026-02-14 · 4 obs
○ 2018-07-11 00:07:02
● 2026-02-14 22:58:48
○ 2026-02-15 19:13:28
○ 2026-02-15 19:13:30
○A13.226.238.222026-02-14 → 2026-02-14 · 4 obs
○ 2018-07-11 00:07:02
● 2026-02-14 22:58:48
○ 2026-02-15 19:13:28
○ 2026-02-15 19:13:30
○A13.226.238.792026-02-14 → 2026-02-14 · 4 obs
○ 2018-07-11 00:07:02
● 2026-02-14 22:58:48
○ 2026-02-15 19:13:28
○ 2026-02-15 19:13:30
○A13.226.238.802026-02-14 → 2026-02-14 · 4 obs
○ 2018-07-11 00:07:02
● 2026-02-14 22:58:48
○ 2026-02-15 19:13:28
○ 2026-02-15 19:13:30
●A13.32.241.292026-02-15 → 2026-02-15 · 3 obs
○ 2026-02-14 22:58:48
● 2026-02-15 19:13:28
● 2026-02-15 19:13:30
●A13.32.241.412026-02-15 → 2026-02-15 · 3 obs
○ 2026-02-14 22:58:48
● 2026-02-15 19:13:28
● 2026-02-15 19:13:30
●A13.32.241.492026-02-15 → 2026-02-15 · 3 obs
○ 2026-02-14 22:58:48
● 2026-02-15 19:13:28
● 2026-02-15 19:13:30
●A13.32.241.952026-02-15 → 2026-02-15 · 3 obs
○ 2026-02-14 22:58:48
● 2026-02-15 19:13:28
● 2026-02-15 19:13:30
○A69.89.86.1452015-07-14 → 2018-07-11 · 4 obs
● 2015-07-14 11:05:14
● 2018-07-11 00:07:02
○ 2026-02-14 22:58:48
○ 2026-02-15 19:13:30

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
why203k.comns-21.awsdns-02.com, ns-917.awsdns-50.net, ns-1033.awsdns-01.org, ns-1926.awsdns-48.co.uk1 record

✅ Authoritative Response

Server: 205.251.199.134

NS records: ns-21.awsdns-02.com, ns-917.awsdns-50.net, ns-1033.awsdns-01.org, ns-1926.awsdns-48.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for why203k.com (unsigned zone)

⏱️ Timing

Total: 622ms | Queries: -

📄 Records

TypeCountSample Data
A413.32.241.49, 13.32.241.29...
NS4ns-1033.awsdns-01.org, ns-1926.awsdns-48.co.uk...
SOA1ns-1926.awsdns-48.co.uk awsdns-hostmaste

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns-21.awsdns-02.com)

AI analysis

why203k.com points to four IP numbers: 13.32.241.29, 13.32.241.41, 13.32.241.49 and 13.32.241.95.

For instance, other host names mantabase.org, asbclouduat.com, stewartdimondfuneraldirectors.co.uk, d2tb9uk5gdyq1k.cloudfront.net and aanvraagcoronacompensatiepremie.be share IP numbers with why203k.com.

why203k.com is delegated to four name servers: ns-21.awsdns-02.com, ns-917.awsdns-50.net, ns-1033.awsdns-01.org and ns-1926.awsdns-48.co.uk.

why203k.com shares name servers with other domains at least partially, for example sakarisms.com, jinyu-kai.com, ana-miler.info, virtualquarry.com and dlstech.com.br.

These name servers are commonly used alongside ns-857.awsdns-43.net, ns-2043.awsdns-63.co.uk, ns-694.awsdns-22.net, ns-1542.awsdns-00.co.uk, ns-380.awsdns-47.com and ns-1520.awsdns-62.org.

Host names with two IP numbers:

ns-21.awsdns-02.com points to: 2600:9000:5300:1500::1 and 205.251.192.21

ns-917.awsdns-50.net points to: 2600:9000:5303:9500::1 and 205.251.195.149

ns-1033.awsdns-01.org points to: 2600:9000:5304:900::1 and 205.251.196.9

ns-1926.awsdns-48.co.uk points to: 2600:9000:5307:8600::1 and 205.251.199.134

Five mail servers handle why203k.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

why203k.com shares mail servers with other domains at least partially; for instance invisioncommunity.com, ns500742.ns500742.ns500731.ns500731.ns500731.ns500731.ns500671.ns500704.ns500671.ns500704.ns500678.ns500671.ns500678.ns500666.ns500291.ns500131.lustychickser.com, ns500734.ns500734.ns500693.ns500699.ns500734.ns500728.ns500693.ns500683.ns500699.ns500683.ns500632.ns500632.ns500588.ns500112.dtrkdll.com, ns500742.ns500742.ns500754.ns500671.ns500704.ns500731.ns500705.ns500705.ns500671.ns500705.ns500678.ns500649.tenderladiesbz.com and ns500734.ns500699.ns500734.ns500699.ns500699.ns500699.ns500588.ns500588.ns500588.ns500588.ns500588.ns500632.ns500632.ns500612.ns500578.ns500110.dtrkdll.com.

these mail servers are commonly used alongside aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.26

alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.27

alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.27

alt3.aspmx.l.google.com points to 2607:f8b0:4024:c0d::1a and 192.178.152.27

alt4.aspmx.l.google.com points to 2607:f8b0:4023:403::1a and 142.250.96.27