Hostname
lolking.net
Last fetched
lolking.net resolves to 13.227.192.117, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. lolking.net 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
- 13.227.192.117
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.57
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.71
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.9
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.33.187.110
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.26
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.29
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 13.33.187.37
13.33.186.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.192.106
18.66.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.66.192.107
18.66.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.66.192.57
18.66.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.66.192.67
18.66.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 99.84.234.101
99.84.232.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 99.84.234.127
99.84.232.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 99.84.234.32
99.84.232.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 99.84.234.49
99.84.232.0/22 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 99.84.91.24
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.44
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.72
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.94
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
IPv6 resolution
No AAAA record for lolking.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- ******** ******** (see notes section below on how to view unmasked data)
- Contact emails
- ********@*****.***, domains@zam.com, 074a3cc4-a0cd-4988-8e33-d4302a7b9dd5@identity-protect.org, 672ff965-48e3-4dae-8d69-0893bc1d2dcd@identity-protect.org, 6a86ae18-57ad-4f47-b163-fea715bbe644@identity-protect.org, 7322aa16-84d0-415e-b1ec-96229d2f0dc7@identity-protect.org, 8018e6da-ff03-4d23-824f-b33ddba59571@identity-protect.org, becec7b9-ecaa-4a17-a459-1292658c1d4c@identity-protect.org, e5430ab6-4eaa-4499-b901-728f610250ee@identity-protect.org, owner-1451694@lolking.net.whoisprivacyservice.org, owner-5214460@lolking.net.whoisprivacyservice.org, owner-5742932@lolking.net.whoisprivacyservice.org, owner-6859868@lolking.net.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| css.lolking.net |
| g00.lolking.net |
| goo.lolking.net |
| help.lolking.net |
| img.lolking.net |
| static.lolking.net |
| u003ewww.lolking.net |
| wildcard.lolking.net |
| www.lolking.net |
Showing 9 of 9 subdomains (9 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
Sample outbound links
Mail and authentication
Nameservers
- ns-215.awsdns-26.com
- ns-578.awsdns-08.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
- ns-1427.awsdns-50.org
- ns-1665.awsdns-16.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: sendgrid.net
- include: mailgun.org
Threat-feed evidence
History
Related pages
Pivot from lolking.net 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: "lolking.net"})-[: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.