Hostname

lordflims.link

Last fetched Tue, 15 Sep 2026 08:35:25 GMT

lordflims.link resolves to 139.162.174.209, announced in 139.162.160.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in DE. lordflims.link 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

Resolution chain

139.162.174.209
139.162.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
139.162.181.76
139.162.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
172.104.149.86
172.104.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
172.104.203.186
172.104.202.0/23 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
172.104.251.198
172.104.224.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
192.155.84.236
192.155.80.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
23.239.3.104
23.239.0.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
23.239.4.93
23.239.0.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
66.175.209.179
66.175.208.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US
66.175.216.36
66.175.216.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
74.207.241.245
74.207.240.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
96.126.111.165
96.126.104.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US

IPv6 resolution

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar: iana:49
Registrant organisation: whois privacy protection service by onamae.com

Mail and authentication

Nameservers

hehua.ns.giantpanda.com
qizai.ns.giantpanda.com
dns1.onamae-expired.com
dns2.onamae-expired.com
ns01.trs-dns.com
ns10.trs-dns.info
ns01.trs-dns.net
ns10.trs-dns.org

Threat-feed evidence

History

Pivot from lordflims.link 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: "lordflims.link"})-[: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.