Skip to content

Hostname

longolexus.com

Last fetched

longolexus.com resolves to 199.232.192.247, announced in 199.232.192.0/22 by FASTLY - Fastly, Inc. in CA. longolexus.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 · longolexus.comRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/longolexus.com

Resolution chain

IPv6 resolution

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

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:299
Registrant organisation
domain administrator
Contact emails
domains@penskecorp.com, postmaster@penskecorp.com

Subdomains

Subdomain
express.longolexus.com
link.longolexus.com
monogram.longolexus.com
parts-dev.longolexus.com
parts-stg.longolexus.com
parts.longolexus.com
partsstore.longolexus.com
www.longolexus.com

Showing 8 of 8 subdomains (8 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • dns1.cscdns.net
  • dns2.cscdns.net
  • 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

  • mxa-00005601.gslb.pphosted.com
  • mxb-00005601.gslb.pphosted.com

SPF policy

  • include: %{ir}.%{v}.%{d}.spf.has.pphosted.com

Threat-feed evidence

History

Related pages

Pivot from longolexus.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: "longolexus.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.