Skip to content

Hostname

paketabikes.com

Last fetched

paketabikes.com resolves to 172.234.24.211, announced in 172.234.16.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. paketabikes.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · paketabikes.comRouting diversity1.5/10Peering density6.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/paketabikes.com

Resolution chain

IPv6 resolution

No AAAA record for paketabikes.com is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
brian muncaster
Contact emails
brianmuncaster@merchantengine.com, bca66323a7f54f7bbccbb127644e7c77.protect@whoisguard.com, 65e28fce751d406e8a8497ec3ff9f0f1.protect@withheldforprivacy.com, reactivation-pending@mail.withheldforprivacy.com

Subdomains

Subdomain
cpanel.paketabikes.com
cpcalendars.paketabikes.com
cpcontacts.paketabikes.com
mail.paketabikes.com
webdisk.paketabikes.com
webmail.paketabikes.com
www.paketabikes.com

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • emily.ns.cloudflare.com
  • huxley.ns.cloudflare.com
  • dns101.registrar-servers.com
  • dns102.registrar-servers.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mx.plingest.com

Threat-feed evidence

History

Related pages

Pivot from paketabikes.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "paketabikes.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.