slenke.com - robtex.com

slenke.com

DNSSEC⚠️ Not signed
A142.44.167.0πŸ‡¨πŸ‡¦ OVH142.44.128.0/17 Hosting route
NSns1.mydomain.com ⭐
A172.64.52.99πŸ‡ΊπŸ‡Έ Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.mydomain.com
A172.64.53.76πŸ‡ΊπŸ‡Έ Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
MXaspmx.l.google.com ⭐
A2607:f8b0:4023:c03::1aπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRdy-in-f26.1e100.net
A142.250.141.27πŸ‡ΊπŸ‡Έ Google142.250.141.0/24
PTRdd-in-f27.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1bπŸ‡¨πŸ‡± Google2800:3f0:4003::/48
A108.177.123.27πŸ‡ΊπŸ‡Έ Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXalt2.aspmx.l.google.com(5)
A2607:f8b0:4023:3003::1aπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRyulnkjt-in-f26.1e100.net
A172.253.145.27πŸ‡ΊπŸ‡Έ Google172.253.145.0/24
PTRyulnkjt-in-f27.1e100.net
MXalt3.aspmx.l.google.com(10)
A2607:f8b0:4023:1015::1aπŸ‡ΊπŸ‡Έ Google2607:f8b0::/32
PTRyudfwta-in-f26.1e100.net
A172.253.135.27πŸ‡ΊπŸ‡Έ Google172.253.135.0/24
PTRyudfwta-in-f27.1e100.net
MXalt4.aspmx.l.google.com(10)
A2607:f8b0:4001:c70::1bπŸ‡ΊπŸ‡Έ Google2607:f8b0:4001::/48
PTRyucbful-in-f27.1e100.net
A192.178.209.26πŸ‡ΊπŸ‡Έ Google192.178.209.0/24
PTRyucbful-in-f26.1e100.net
TXTgoogle-site-verification=QIEge9qryOAU70iRsjNkYNB36o4IOsqDHqD4XtgXcAE
TXTv=spf1 ip4:142.44.167.0 include:_spf.google.com include:zoho.com ~all
TXTstripe-verification=64de23f9e2539236ccd7aef313b0d70abb8cfe63a2761d8613ab364f3...
SOAns1.mydomain.comdnsadmin@mydomain.com 2014-10-16 #65

com

Same first word

Similar names

DNS History

13 records (8 active, 5 former)

2017201820192020202120222023202420252026NSns1.mydomain.comns2.mydomain.comns1.slenke.comns2.slenke.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.commx.zoho.commx2.zoho.comA142.44.167.0208.75.75.40
●NSns1.mydomain.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
β—‹NSns1.slenke.com2016-12-18 β†’ 2017-08-22 Β· 4 obs
● 2016-12-18 08:09:24
● 2017-08-22 05:12:56
β—‹ 2026-04-16 18:58:34
β—‹ 2026-05-11 04:32:58
●NSns2.mydomain.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
β—‹NSns2.slenke.com2016-12-18 β†’ 2017-08-22 Β· 4 obs
● 2016-12-18 08:09:24
● 2017-08-22 05:12:56
β—‹ 2026-04-16 18:58:34
β—‹ 2026-05-11 04:32:58
●MXalt1.aspmx.l.google.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
●MXalt2.aspmx.l.google.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
●MXalt3.aspmx.l.google.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
●MXalt4.aspmx.l.google.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
●MXaspmx.l.google.com2026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
β—‹MXmx.zoho.com2016-12-18 β†’ 2017-08-22 Β· 4 obs
● 2016-12-18 08:09:24
● 2017-08-22 05:12:56
β—‹ 2026-04-16 18:58:34
β—‹ 2026-05-11 04:32:58
β—‹MXmx2.zoho.com2016-12-18 β†’ 2017-08-22 Β· 4 obs
● 2016-12-18 08:09:24
● 2017-08-22 05:12:56
β—‹ 2026-04-16 18:58:34
β—‹ 2026-05-11 04:32:58
●A142.44.167.02026-04-16 β†’ 2026-05-11 Β· 3 obs
β—‹ 2017-08-22 05:12:56
● 2026-04-16 18:58:34
● 2026-05-11 04:32:58
β—‹A208.75.75.402016-12-18 β†’ 2017-08-22 Β· 4 obs
● 2016-12-18 08:09:24
● 2017-08-22 05:12:56
β—‹ 2026-04-16 18:58:34
β—‹ 2026-05-11 04:32:58

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
slenke.comns1.mydomain.com, ns2.mydomain.com2 records

βœ… Authoritative Response

Server:172.64.53.76

NS records: ns1.mydomain.com, ns2.mydomain.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for slenke.com (unsigned zone)

⏱️ Timing

Total: 394ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1142.44.167.0
NS2ns1.mydomain.com, ns2.mydomain.com
MX5aspmx.l.google.com (pri: 1), alt4.aspmx.l.google.com (pri: 10)...
TXT3v=spf1 ip4:142.44.167.0 include:_spf.goo, google-site-verification=QIEge9qryOAU70i...
SOA1ns1.mydomain.com dnsadmin.mydomain.com

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.mydomain.com, ns2.mydomain.com)

Analysis

IP Addresses

slenke.com maps to IP address 142.44.167.0.

Name Servers

Two name servers ns1.mydomain.com and ns2.mydomain.com are delegated to slenke.com.

slenke.com uses the same name server configuration as other domains, such as radprops.com, fpcn.com, ponzospizza.co, festivaldetheatre.com and earthtechexpo.com.

slenke.com at least partially shares name servers with other domains such as hotramhotelresorts.com, patriciahausner.com, dkfs.com, e-bench.com and etrobbins.com.

these name servers are commonly used alongside the name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com, ns2.yourhostingaccount.com and ns1.fatcow.com.

Host names with a single IP address:

ns1.mydomain.com points to 172.64.52.99

ns2.mydomain.com points to 172.64.53.76

Mail Servers

slenke.com is handled by five mail servers: 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.

slenke.com shares mail servers with other domains at least in part, for instance marcgirod.com, ns500734.ns500734.ns500699.ns500693.ns500734.ns500693.ns500699.ns500693.ns500632.ns500612.ns500612.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com, ns500765.ns500734.ns500734.ns500734.ns500734.ns500699.ns500699.ns500699.ns500699.ns500699.ns500693.ns500699.ns500699.ns500683.ns500612.ns500110.dtrkdll.com, ns500671.ns500671.ns500754.ns500731.ns500742.ns500704.ns500688.ns500671.ns500705.ns500705.ns500649.ns500649.ns500153.tenderladiesbz.com and ns500758.ns500758.ns500759.ns500698.ns500698.ns500698.ns500698.ns500698.ns500736.ns500736.ns500576.ns500698.ns500576.ns500698.ns500576.ns500576.trackreceptor.com.

these mail servers are often used together with aspmx2.googlemail.com, aspmx3.googlemail.com and smtp.google.com.

Two IPs per host name:

aspmx.l.google.com points to: 2607:f8b0:4023:c03::1a and 142.250.141.27

alt1.aspmx.l.google.com points to: 2800:3f0:4003:c0f::1b and 108.177.123.27

alt2.aspmx.l.google.com points to: 2607:f8b0:4023:3003::1a and 172.253.145.27

alt3.aspmx.l.google.com points to: 2607:f8b0:4023:1015::1a and 172.253.135.27

alt4.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1b and 192.178.209.26

Pattern: left IDs ascend by 9 (12, 21, 30, 39, 48); each pair of targets ascend by 9 (15/18, 24/27, 33/36, 42/45, 51/54)