Skip to content

Hostname

nextbet.com

Last fetched

nextbet.com resolves to 13 IPv4 addresses operated by AKAMAI-ASN1 in DE. WHOIS lists iana:472 as the registrar.

Nutrition Label

WHISPER CANON · nextbet.comRouting diversity4.2/10Peering density8.8/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/nextbet.com

Resolution chain

nextbet.com resolves to 13 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
2.16.241.162.16.241.0/24AS20940AKAMAI-ASN1DE
2.16.241.192.16.241.0/24AS20940AKAMAI-ASN1DE
2.19.126.1362.19.126.0/24AS20940AKAMAI-ASN1DE
2.19.126.1542.19.126.0/24AS20940AKAMAI-ASN1DE
2.19.126.1632.19.126.0/24AS20940AKAMAI-ASN1DE
23.2.13.5023.2.13.0/24AS20940AKAMAI-ASN1DE
23.2.13.5923.2.13.0/24AS20940AKAMAI-ASN1DE
23.200.0.17423.200.0.0/24AS20940AKAMAI-ASN1US
23.200.0.19023.200.0.0/24AS20940AKAMAI-ASN1US
23.32.238.21923.32.238.0/23AS20940AKAMAI-ASN1DE
23.32.238.24023.32.238.0/23AS20940AKAMAI-ASN1DE
23.55.163.1223.55.163.0/24AS20940AKAMAI-ASN1DE
23.55.163.1823.55.163.0/24AS20940AKAMAI-ASN1DE

WHOIS identity

Registrar
iana:472
Organization
domain trustees
Contact emails

Subdomains

15 observed subdomains of nextbet.com.

Subdomain
aka-pay.nextbet.com
www-stg2.nextbet.com
www.nextbet.com
stg.nextbet.com
sports.nextbet.com
smtpmd01.nextbet.com
pay.nextbet.com
mobile-stg2.nextbet.com
mobile.nextbet.com
m.nextbet.com
dev2.nextbet.com
bbproxy2-stg-aka.nextbet.com
bbproxy-stg.nextbet.com
aka-www.nextbet.com
aka-sports.nextbet.com

Web-graph footprint

Distinct hostnames that link to or from nextbet.com in the public web crawl.

167 sites link to this hostname.

Sample inbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

3 SPF mechanisms authorising senders for nextbet.com.

MechanismTarget
SPF_INCLUDE_spf.google.com
SPF_IP202.129.222.239
SPF_IP202.129.222.240

Related pages

Pivot deeper into the graph from nextbet.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

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

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