You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are domains in reserved list and domains reserved for winners of the particular auctions in which case correct registration code is required to be able to register that domain.
Currently registrars have no automated way of knowing if any such restrictions apply to a domain. EPP info request says no found as there is no such domain registered and check request returns avail = 1 as the domain is available for registration. The only way to know about any such restrictions is via WHOIS.
Lets add additional info to GET /repp/v1/domains/:domain_name response in case the domain is not registered (if that approach makes makes architecture complicated consider adding new endpoint for simple epp check type requests)
There are domains in reserved list and domains reserved for winners of the particular auctions in which case correct registration code is required to be able to register that domain.
Currently registrars have no automated way of knowing if any such restrictions apply to a domain. EPP info request says no found as there is no such domain registered and check request returns avail = 1 as the domain is available for registration. The only way to know about any such restrictions is via WHOIS.
Lets add additional info to GET /repp/v1/domains/:domain_name response in case the domain is not registered (if that approach makes makes architecture complicated consider adding new endpoint for simple epp check type requests)
so instead of domain not found we could return:
{
"code": 1000,
"message": "Command completed successfully",
"data": {
"domain": {
"name": "biz.ee",
"available": true
}
}
}
and in case of restrictions
{
"code": 1000,
"message": "Command completed successfully",
"data": {
"domain": {
"name": "biz.ee",
"reserved": true,
"available": true
}
}
}
reserved element could actually be implemented for all get domain data requests as a reserved domain can be registered at the same time. For example:
{
"code": 1000,
"message": "Command completed successfully",
"data": {
"domain": {
"name": "biz.ee",
"registrant": {
"name": "KARL",
"code": "ATSAA:749AA80F"
},
"created_at": "2021-01-15T12:07:20.079+02:00",
"updated_at": "2021-01-21T16:41:59.707+02:00",
"expire_time": "2023-01-16T00:00:00.000+02:00",
"outzone_at": null,
"delete_date": null,
"force_delete_date": null,
"contacts": [
{
"code": "ATSAA:C7A52A30",
"type": "AdminDomainContact",
"name": "KARL"
},
{
"code": "ATSAA:CC53EF9C",
"type": "TechDomainContact",
"name": "KARL"
}
],
"nameservers": [],
"dnssec_keys": [],
"statuses": {
"inactive": ""
},
"registrar": {
"name": "Kreative Digital OÜ",
"website": "https://kreative.ee"
},
"dispute": false,
"reserved": false,
"transfer_code": "2f81ec671b69a2aa5d6375631e259ae7",
}
}
}
The text was updated successfully, but these errors were encountered: