IPv4 Addresses
nextcore-consulting.com. 300 IN A 104.21.64.37 nextcore-consulting.com. 300 IN A 172.67.175.233
IPv6 Addresses
nextcore-consulting.com. 300 IN AAAA 2606:4700:3031:0:0:0:AC43:AFE9 nextcore-consulting.com. 300 IN AAAA 2606:4700:3033:0:0:0:6815:4025
Name Servers
nextcore-consulting.com. 1200 IN NS cesar.ns.cloudflare.com. nextcore-consulting.com. 1200 IN NS emely.ns.cloudflare.com.
Mail Servers
nextcore-consulting.com. 300 IN MX 1 smtp.google.com.
SOA Details
nextcore-consulting.com. 1200 IN SOA cesar.ns.cloudflare.com. dns.cloudflare.com. 2411262283 10000 2400 604800 1800
Certificate Authority Authorization
No CAA records were returned at this registrable domain name. With no CAA policy, any public certificate authority (CA) may issue TLS certificates for names under this zone unless a parent publishes CAA; add issue / issuewild / iodef records to restrict issuance.
DMARC
Organizational policy (p): how receivers treat mail that fails aligned DMARC checks — none (monitor only), quarantine (often junk), or reject (block).
pct: share of mail that gets quarantine/reject; 100 = all failing messages (default).
100Aggregate DMARC reports (ZIP/XML). Optional but recommended for visibility.
Forensic (per-failure) reports. Often omitted for privacy or volume.
nextcore-consulting.com. 300 IN DMARC v=DMARC1; p=none;
DKIM
nextcore-consulting.com. 300 IN DKIM v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuZJQOBT5bBSWMk/1pu6gGKsaPAjiFDGbkHYMC5Jz1vovTAaFp3ve1cffX0ggK0rv2ma3NwvO78eEVq1+32HmvC6hKX4qeF/RU68RyvIbPhEjGyu1lq3gSV5PJfSvMARdcSuyvpheVx1jv0ibQqKeqnOLqRgbvOhRQqnVDbw0aeqg9lCYfP+Azrfp/1zLapjkAVFH+OQxyvWX5hlHWKZHmgR+zvMUdadXpRMuEXD00fNr5hxb2RCwCaYV0oPoujqgKbe4UzuBAAdEzX4tdl5EJNQS/3j6U+EBK1SbKrXnw9Usfua+eQQ4UiSiW+Crh74S/koQXaNr4nKI/35Jyr7NdwIDAQAB
SPF (Sender Policy Framework)
| Qualifier | Mechanism | Target / value | Valid | Details |
|---|---|---|---|---|
| + Pass | include |
|
||
| ~ Softfail | all |
—
|
|
nextcore-consulting.com. 300 IN TXT "v=spf1 include:_spf.google.com ~all"
MTA-STS
This hostname does not publish an MTA-STS policy (no v=STSv1 TXT at _mta-sts.<name> and/or no policy at https://mta-sts.<name>/.well-known/mta-sts.txt).