Hostname
bernardperroud.com
Last fetched
bernardperroud.com resolves to 139.162.174.209, announced in 139.167.138.0/23 by AKAMAI-LINODE-AP - Akamai Connected Cloud in DE. bernardperroud.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 139.162.174.209
139.167.138.0/23 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 139.162.181.76
139.167.138.0/23 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 172.104.149.86
172.109.207.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 172.104.203.186
172.110.0.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 172.104.251.198
172.110.0.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 66.175.209.179
66.178.64.0/18 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US
- 96.126.111.165
96.127.242.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US
IPv6 resolution
No AAAA record for bernardperroud.com is recorded in WhisperGraph.
Attribution
akamai linode ap connected
ORIGIN_AS
WHOIS identity
- Registrar
- iana:940
- Registrant organisation
- aubry pascal
- Contact emails
- bernardperroud.com@privacy.above.com, milenradumilo@gmail.com, 01luqh53myyvt6cov2l6@f.o-w-o.info, 9bybez4bfq7pa44wugk3@i.o-w-o.info, 9ndc9hrjn796jklgtalr@r.o-w-o.info
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- anan.ns.giantpanda.com
- po.ns.giantpanda.com
MX records
- mail.mailerhost.net
SPF policy
- ip: fd43:c0d1:c090::/48
Threat-feed evidence
History
Related pages
Pivot from bernardperroud.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: "bernardperroud.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.